se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall/Spring |
Prerequisites |
| ||||||||
Course Language | |||||||||
Course Type | Elective | ||||||||
Course Level | - | ||||||||
Mode of Delivery | - | ||||||||
Teaching Methods and Techniques of the Course | Problem SolvingCase StudyApplication: Experiment / Laboratory / Workshop | ||||||||
Course Coordinator | |||||||||
Course Lecturer(s) | |||||||||
Assistant(s) |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction | Silberschatz, Chapter 1 |
2 | Operating System Structures | Silberschatz, Chapter 2 |
3 | Processes | Silberschatz, Chapter 3 |
4 | Threads | Silberschatz, Chapter 4 |
5 | CPU Scheduling | Silberschatz, Chapter 5 |
6 | Process Synchronization | Silberschatz, Chapter 6 |
7 | Deadlocks | Silberschatz, Chapter 7 |
8 | Arasınav/ Midterm | |
9 | Main Memory | Silberschatz, Chapter 8 |
10 | Virtual Memory | Silberschatz,Chapter 9 |
11 | File System Interface | Silberschatz, Chapter 10 |
12 | File System Implementation | Silberschatz, Chapter 11 |
13 | Mass Storage Structure | Silberschatz, Chapter 12 |
14 | I/O Systems | Silberschatz, Chapter 13 |
15 | Review of the Semester | |
16 | Review of the Semester |
Course Notes/Textbooks | A. Silberschatz, P.B. Galvin and Greg Gagne “Operating System Concepts”, 7th Ed., Wiley, 2008 |
Suggested Readings/Materials | A. Tanenbaum, “Modern Operating Systems”, 3rd. Ed. PrenticeHall, 2007W. Stallings, “Operating Systems: Internals and Design Principles” 6th Ed., PrenticeHall, 2008. |
Semester Activities | Number | Weigthing |
Participation | 14 | 10 |
Laboratory / Application | 8 | 15 |
Field Work | ||
Quizzes / Studio Critiques | 1 | 15 |
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 25 |
Final Exam | 1 | 35 |
Total |
Weighting of Semester Activities on the Final Grade | 65 | |
Weighting of End-of-Semester Activities on the Final Grade | 35 | |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | 2 | |
Study Hours Out of Class | 15 | 2 | |
Field Work | |||
Quizzes / Studio Critiques | 1 | 15 | |
Portfolio | |||
Homework / Assignments | |||
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 7 | |
Final Exams | 1 | 10 | |
Total | 142 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | |||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | |||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | |||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | |||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | |||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest